Method and apparatus for providing emergency calls to a disabled endpoint device

ABSTRACT

The present invention enables the remote activation of a device by a packet-switched service, e.g., VoIP network service for the purposes of receiving calls identified as urgent from a pre-identified calling party when the device is disabled. The present invention enables registered users to select the calling parties they wish to receive emergency calls from.

The present invention relates generally to communication networks and,more particularly, to a method and apparatus enabling emergency calls toreach a disabled endpoint device in packet-switched networks, e.g.,Voice over Internet Protocol (VoIP) networks.

BACKGROUND OF THE INVENTION

Users of packet-switched network services, e.g., VoIP network servicescan turn off their devices that they use to access network services.This capability is extremely convenient for users who are unavailable toanswer incoming calls. Occasionally, however, users will need to receiveemergency or critical calls even though they desire to be uninterruptedfor all other call types.

Therefore, a need exists for a method and apparatus for enablingemergency calls to reach a disabled endpoint device in packet-switchednetworks, e.g., Voice over Internet Protocol (VoIP) networks.

SUMMARY OF THE INVENTION

In one embodiment, the present invention enables the remote activationof a device by a packet-switched network service, e.g., VoIP networkservice for the purposes of receiving calls identified as urgent from apre-identified calling party when the device is disabled. The presentinvention enables registered users to select the calling parties theywish to receive emergency calls from.

BRIEF DESCRIPTION OF THE DRAWINGS

The teaching of the present invention can be readily understood byconsidering the following detailed description in conjunction with theaccompanying drawings, in which:

FIG. 1 illustrates an exemplary Voice over Internet Protocol (VoIP)network related to the present invention;

FIG. 2 illustrates a flowchart of a method for registering emergencycalls to disabled endpoint device feature in a VoIP network of thepresent invention;

FIG. 3 illustrates a flowchart of a method for enabling emergency callsto disabled endpoint device in a VoIP network of the present invention;and

FIG. 4 illustrates a high level block diagram of a general purposecomputer suitable for use in performing the functions described herein.

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures.

DETAILED DESCRIPTION

To better understand the present invention, FIG. 1 illustrates anexample network, e.g., a packet-switched network such as a VoIP networkrelated to the present invention. The VoIP network may comprise varioustypes of customer endpoint devices connected via various types of accessnetworks to a carrier (a service provider) VoIP core infrastructure overan Internet Protocol/Multi-Protocol Label Switching (IP/MPLS) based corebackbone network. Broadly defined, a VoIP network is a network that iscapable of carrying voice signals as packetized data over an IP network.An IP network is broadly defined as a network that uses InternetProtocol to exchange data packets.

The customer endpoint devices can be either Time Division Multiplexing(TDM) based or IP based. TDM based customer endpoint devices 122, 123,134, and 135 typically comprise of TDM phones or Private Branch Exchange(PBX). IP based customer endpoint devices 144 and 145 typically compriseIP phones or PBX. The Terminal Adaptors (TA) 132 and 133 are used toprovide necessary interworking functions between TDM customer endpointdevices, such as analog phones, and packet based access networktechnologies, such as Digital Subscriber Loop (DSL) or Cable broadbandaccess networks. TDM based customer endpoint devices access VoIPservices by using either a Public Switched Telephone Network (PSTN) 120,121 or a broadband access network via a TA 132 or 133. IP based customerendpoint devices access VoIP services by using a Local Area Network(LAN) 140 and 141 with a VoIP gateway or router 142 and 143,respectively.

The access networks can be either TDM or packet based. A TDM PSTN 120 or121 is used to support TDM customer endpoint devices connected viatraditional phone lines. A packet based access network, such as FrameRelay, ATM, Ethernet or IP, is used to support IP based customerendpoint devices via a customer LAN, e.g., 140 with a VoIP gateway androuter 142. A packet based access network 130 or 131, such as DSL orCable, when used together with a TA 132 or 133, is used to support TDMbased customer endpoint devices.

The core VoIP infrastructure comprises of several key VoIP components,such the Border Element (BE) 112 and 113, the Call Control Element (CCE)111, and VoIP related servers 114. The BE resides at the edge of theVoIP core infrastructure and interfaces with customers endpoints overvarious types of access networks. A BE is typically implemented as aMedia Gateway and performs signaling, media control, security, and calladmission control and related functions. The CCE resides within the VoIPinfrastructure and is connected to the BEs using the Session InitiationProtocol (SIP) over the underlying IP/MPLS based core backbone network110. The CCE is typically implemented as a Media Gateway Controller andperforms network wide call control related functions as well asinteracts with the appropriate VoIP service related servers whennecessary. The CCE functions as a SIP back-to-back user agent and is asignaling endpoint for all call legs between all BEs and the CCE. TheCCE may need to interact with various VoIP related servers in order tocomplete a call that require certain service specific features, e.g.translation of an E.164 voice network address into an IP address.

For calls that originate or terminate in a different carrier, they canbe handled through the PSTN 120 and 121 or the Partner IP Carrier 160interconnections. For originating or terminating TDM calls, they can behandled via existing PSTN interconnections to the other carrier. Fororiginating or terminating VoIP calls, they can be handled via thePartner IP carrier interface 160 to the other carrier.

In order to illustrate how the different components operate to support aVoIP call, the following call scenario is used to illustrate how a VoIPcall is setup between two customer endpoints. A customer using IP device144 at location A places a call to another customer at location Z usingTDM device 135. During the call setup, a setup signaling message is sentfrom IP device 144, through the LAN 140, the VoIP Gateway/Router 142,and the associated packet based access network, to BE 112. BE 112 willthen send a setup signaling message, such as a SIP-INVITE message if SIPis used, to CCE 111. CCE 111 looks at the called party information andqueries the necessary VoIP service related server 114 to obtain theinformation to complete this call. If BE 113 needs to be involved incompleting the call; CCE 111 sends another call setup message, such as aSIP-INVITE message if SIP is used, to BE 113. Upon receiving the callsetup message, BE 113 forwards the call setup message, via broadbandnetwork 131, to TA 133. TA 133 then identifies the appropriate TDMdevice 135 and rings that device. Once the call is accepted at locationZ by the called party, a call acknowledgement signaling message, such asa SIP-ACK message if SIP is used, is sent in the reverse direction backto the CCE 111. After the CCE 111 receives the call acknowledgementmessage, it will then send a call acknowledgement signaling message,such as a SIP-ACK message if SIP is used, toward the calling party. Inaddition, the CCE 111 also provides the necessary information of thecall to both BE 112 and BE 113 so that the call data exchange canproceed directly between BE 112 and BE 113. The call signaling path 150and the call data path 151 are illustratively shown in FIG. 1. Note thatthe call signaling path and the call data path are different becauseonce a call has been setup up between two endpoints, the CCE 111 doesnot need to be in the data path for actual direct data exchange.

Note that a customer in location A using any endpoint device type withits associated access network type can communicate with another customerin location Z using any endpoint device type with its associated networktype as well. For instance, a customer at location A using IP customerendpoint device 144 with packet based access network 140 can callanother customer at location Z using TDM endpoint device 123 with PSTNaccess network 121. The BEs 112 and 113 are responsible for thenecessary signaling protocol translation, e.g., SS7 to and from SIP, andmedia format conversion, such as TDM voice format to and from IP basedpacket voice format.

Users of packet-switched network services, e.g., VoIP network services,can turn off their devices that they use to access network services.This capability is extremely convenient for users who are unavailable toanswer incoming calls. Occasionally, however, users will need to receiveemergency or critical calls even though they desire to be uninterruptedfor all other call types.

To address this need, the present invention enables the remoteactivation of a device by a VoIP network service for the purposes ofreceiving calls identified as urgent from a pre-identified calling partywhen the device is disabled. The present invention enables registeredusers to select the calling parties they wish to receive “emergency”calls from.

Returning to FIG. 1, a user using IP endpoint device 144 has subscribedto the emergency calls to disabled endpoint device service feature andhas registered endpoint device 144 for the service feature. The user hasdisabled the device to be uninterrupted, i.e., the disabled devicecannot receive or initial calls. This disabled state can be perceived asa standby state or a sleep state, where the endpoint device is consumingvery little power. However, the endpoint device 144 supports theemergency calls to disabled endpoint device service feature and can beremotely activated by the network when necessary. The network receives acall from another user using endpoint device 135. CCE 211 checks andfinds out that the call destined to endpoint device 144 has subscribedto the emergency calls to disabled endpoint device service feature andthe calling endpoint device 135 is on the allowed list of emergencycalls or emergency numbers. Therefore, CCE 211 sends a signaling messageto endpoint device 144 to enable the device. CCE 211 also sends an alertusing the user selected alert mechanism previously chosen by the user.CCE 211 repeats periodically the alert until the user answers andaccepts the alert.

FIG. 2 illustrates a flowchart of a method for registering emergencycalls to disabled endpoint device feature by the packet-switchednetwork, e.g., a VoIP network. Method 200 starts in step 205 andproceeds to step 210.

In step 210, the method registers an IP endpoint device to receive theemergency calls to disabled endpoint device service feature. In step220, the method registers the allowed list of calling numbers that thenetwork will enable a turned off endpoint device. In step 230, themethod registers the user selected alert mechanisms that will be used toalert the user. Alert mechanism options include choices of ring tones,vibrations as well as text messages. The method ends in step 240.

FIG. 3 illustrates a flowchart of a method for enabling emergency callsto disabled endpoint device by the CCE in a packet-switched network,e.g., VoIP network. Method 300 starts in step 305 and proceeds to step310.

In step 310, the method receives a call destined to a disabled IPendpoint device that has subscribed to the emergency calls to disabledendpoint device service feature. In step 320, the method checks if thecalling number is on the allowed emergency calling number list. If thecalling number is on the allowed emergency calling number list, themethod proceeds to step 330; otherwise, the method proceeds to step 370.

In step 330, the method activates the disabled endpoint device, e.g.,causing the endpoint device into an “on” state, where the endpointdevice is capable of receiving an incoming call. For example, the methodsends a signaling message to the disabled device to remotely enable theendpoint device.

In step 340, once the disabled endpoint device has been activated, themethod sends an alert (e.g., an alert message) to the remotely enableddevice to alert the user of an incoming emergency call. The form of thealert message is dependent of the capability of the endpoint device,e.g., a type of ringing tone, a vibration, a flashing light indicator,e.g., a LED, a type of color of flashing LED and so on.

In step 350, the method checks if the user has accepted or acknowledgedthe emergency call alert. Acceptance or acknowledgement of the emergencyalert message can be implemented in different manners. Activating theendpoint device to read a text message, activating a button to stop thevibrating feature on the endpoint device, accessing a menu to view“missed calls”, retrieving a voice mail from the communication networkare some examples of accepting or acknowledging the emergency alertmessage. If the alert has not been accepted or acknowledged, then themethod proceeds to step 360; otherwise, the method proceeds to step 380.In step 360, the method waits a predefined period of time and thenproceeds back to step 340. In step 370, the method processes the callusing the called party unavailable service logic configured by the user.This includes, but is not limited to, sending the caller to a voicemailor a network announcement message stating the called party isunavailable at the moment. The method ends in step 380.

Note that the endpoint device must support the emergency calls todisabled endpoint device service feature in order to be remotelyactivated by the network when necessary. For example, the endpointdevice may have an off state that resembles a standby state or sleepstate with low power consumption, where the endpoint device istechnically off. However, under this “semi” or “hybrid” off state, theendpoint device will be unable to receive and/or initiate any calls,except that it can be enabled or activated by a remote signal initiatedby the VoIP network.

FIG. 4 depicts a high level block diagram of a general purpose computersuitable for use in performing the functions described herein. Asdepicted in FIG. 4, the system 400 comprises a processor element 402(e.g., a CPU), a memory 404, e.g., random access memory (RAM) and/orread only memory (ROM), an emergency call to disabled IP endpoint devicemodule 405, and various input/output devices 406 (e.g., storage devices,including but not limited to, a tape drive, a floppy drive, a hard diskdrive or a compact disk drive, a receiver, a transmitter, a speaker, adisplay, a speech synthesizer, an output port, and a user input device(such as a keyboard, a keypad, a mouse, and the like)).

It should be noted that the present invention can be implemented insoftware and/or in a combination of software and hardware, e.g., usingapplication specific integrated circuits (ASIC), a general purposecomputer or any other hardware equivalents. In one embodiment, thepresent emergency call to disabled IP endpoint device module or process405 can be loaded into memory 404 and executed by processor 402 toimplement the functions as discussed above. As such, the presentemergency call to disabled IP endpoint device process 405 (includingassociated data structures) of the present invention can be stored on acomputer readable medium or carrier, e.g., RAM memory, magnetic oroptical drive or diskette and the like.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above-described exemplary embodiments, butshould be defined only in accordance with the following claims and theirequivalents.

1. A method for enabling a disabled endpoint device in a communicationnetwork, comprising: receiving a call destined to the disabled endpointdevice; determining whether a calling number of said call is on a listof emergency numbers; and activating the disabled endpoint device ifsaid calling number is on said list of emergency numbers.
 2. The methodof claim 1, wherein said communication network is a Voice over InternetProtocol (VoIP) network.
 3. The method of claim 1, wherein said call isreceived by a call control element (CCE).
 4. The method of claim 1,wherein said activating comprises: sending a signal to the disabledendpoint device for activating the disabled device.
 5. The method ofclaim 1, further comprising: sending an alert message in accordance withan alert option selected by a subscriber of said disabled endpointdevice.
 6. The method of claim 5, wherein said alert option comprises atleast one of: a type of ring tone, a vibration and a text message. 7.The method of claim 5, wherein said sending is performed on a periodicbasis until an acknowledgement of said alert message is received.
 8. Themethod of claim 1, wherein said list of emergency numbers is registeredby a subscriber.
 9. The method of claim 1, wherein said disabledendpoint device is an internet protocol (IP) endpoint device.
 10. Acomputer-readable medium having stored thereon a plurality ofinstructions, the plurality of instructions including instructionswhich, when executed by a processor, cause the processor to perform thesteps of a method for enabling a disabled endpoint device in acommunication network, comprising: receiving a call destined to thedisabled endpoint device; determining whether a calling number of saidcall is on a list of emergency numbers; and activating the disabledendpoint device if said calling number is on said list of emergencynumbers.
 11. The computer-readable medium of claim 10, wherein saidcommunication network is a Voice over Internet Protocol (VoIP) network.12. The computer-readable medium of claim 10, wherein said call isreceived by a call control element (CCE).
 13. The computer-readablemedium of claim 10, wherein said activating comprises: sending a signalto the disabled endpoint device for activating the disabled device. 14.The computer-readable medium of claim 10, further comprising: sending analert message in accordance with an alert option selected by asubscriber of said disabled endpoint device.
 15. The computer-readablemedium of claim 14, wherein said alert option comprises at least one of:a type of ring tone, a vibration and a text message.
 16. Thecomputer-readable medium of claim 14, wherein said sending is performedon a periodic basis until an acknowledgement of said alert message isreceived.
 17. The computer-readable medium of claim 10, wherein saidlist of emergency numbers is registered by a subscriber.
 18. Thecomputer-readable medium of claim 10, wherein said disabled endpointdevice is an internet protocol (IP) endpoint device.
 19. A system forenabling a disabled endpoint device in a communication network,comprising: means for receiving a call destined to the disabled endpointdevice; means for determining whether a calling number of said call ison a list of emergency numbers; and means for activating the disabledendpoint device if said calling number is on said list of emergencynumbers.
 20. The system of claim 19, wherein said communication networkis a Voice over Internet Protocol (VoIP) network.